Skip to content

OCPCLOUD-3319: Remove capiinstaller controller - #507

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
openshift-cloud-team:remove-capiinstaller
Apr 9, 2026
Merged

OCPCLOUD-3319: Remove capiinstaller controller#507
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
openshift-cloud-team:remove-capiinstaller

Conversation

@mdbooth

@mdbooth mdbooth commented Mar 27, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

@openshift-ci-robot

openshift-ci-robot commented Mar 27, 2026

Copy link
Copy Markdown

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 27, 2026
@openshift-ci-robot

openshift-ci-robot commented Mar 27, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@mdbooth: This pull request references OCPCLOUD-3319 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Requires the new installer to merge first: #494

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 27, 2026
@openshift-ci

openshift-ci Bot commented Mar 27, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai

coderabbitai Bot commented Mar 27, 2026 •
edited
Loading

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 2fb8c633-d252-444c-a8bf-2b0a66e04ef8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci-robot

openshift-ci-robot commented Mar 27, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@mdbooth: This pull request references OCPCLOUD-3319 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Requires the new installer to merge first: #494

TODO:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@mdbooth
mdbooth force-pushed the remove-capiinstaller branch from 1812b00 to 2d1adc0 Compare March 27, 2026 16:27
@openshift-ci-robot

openshift-ci-robot commented Mar 27, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@mdbooth: This pull request references OCPCLOUD-3319 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Requires the new installer to merge first: #494

TODO:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

openshift-ci-robot commented Mar 27, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@mdbooth: This pull request references OCPCLOUD-3319 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Requires the new installer to merge first: #494

TODO:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

openshift-ci-robot commented Mar 27, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@mdbooth: This pull request references OCPCLOUD-3319 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Removes the legacy capiinstaller controller, which still handles transport configmaps. Only ORC that we know of is still using these.

TODO:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

openshift-ci-robot commented Mar 27, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@mdbooth: This pull request references OCPCLOUD-3319 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Removes the legacy capiinstaller controller, which still handles transport configmaps. Only ORC that we know of is still using these.

TODO:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

openshift-ci-robot commented Mar 30, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@mdbooth: This pull request references OCPCLOUD-3319 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Removes the legacy capiinstaller controller, which still handles transport configmaps. Only ORC that we know of is still using these.

TODO:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@mdbooth
mdbooth marked this pull request as ready for review April 2, 2026 16:31
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 2, 2026
@openshift-ci
openshift-ci Bot requested review from chrischdi and damdo April 2, 2026 16:32
damdo
damdo reviewed Apr 9, 2026
View reviewed changes

@damdo damdo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

for testing

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 9, 2026
@openshift-merge-bot

openshift-merge-bot Bot commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-capi-techpreview
/test e2e-aws-ovn
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-techpreview
/test e2e-aws-ovn-techpreview-upgrade
/test e2e-azure-capi-techpreview
/test e2e-azure-ovn-techpreview
/test e2e-azure-ovn-techpreview-upgrade
/test e2e-gcp-capi-techpreview
/test e2e-gcp-ovn-techpreview
/test e2e-metal3-capi-techpreview
/test e2e-openstack-capi-techpreview
/test e2e-openstack-ovn-techpreview
/test e2e-vsphere-capi-techpreview
/test regression-clusterinfra-aws-ipi-techpreview-capi

@openshift-ci

openshift-ci Bot commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 9, 2026
@mdbooth

mdbooth commented Apr 9, 2026

Copy link
Copy Markdown
Contributor Author

This can be verified if all the capi-techpreview jobs pass.

@damdo

damdo commented Apr 9, 2026

Copy link
Copy Markdown
Member

/override ci/prow/e2e-openstack-ovn-techpreview

@openshift-ci

openshift-ci Bot commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

@damdo: Overrode contexts on behalf of damdo: ci/prow/e2e-openstack-ovn-techpreview

Details

In response to this:

/override ci/prow/e2e-openstack-ovn-techpreview

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@damdo

damdo commented Apr 9, 2026

Copy link
Copy Markdown
Member

/verified by e2e-aws-capi-techpreview passing

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 9, 2026
@openshift-ci-robot

openshift-ci-robot commented Apr 9, 2026

Copy link
Copy Markdown

@damdo: This PR has been marked as verified by e2e-aws-capi-techpreview passing.

Details

In response to this:

/verified by e2e-aws-capi-techpreview passing

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@damdo

damdo commented Apr 9, 2026

Copy link
Copy Markdown
Member

/override ci/prow/e2e-aws-ovn

Unrelated failure, this change doesn't run in that job

@openshift-ci

openshift-ci Bot commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

@damdo: Overrode contexts on behalf of damdo: ci/prow/e2e-aws-ovn

Details

In response to this:

/override ci/prow/e2e-aws-ovn

Unrelated failure, this change doesn't run in that job

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 50ba4c2 into openshift:main Apr 9, 2026
23 of 25 checks passed
@mdbooth
mdbooth deleted the remove-capiinstaller branch April 10, 2026 08:23
@lunarwhite lunarwhite mentioned this pull request Apr 10, 2026
Closed
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@damdo damdo damdo left review comments
@chrischdi chrischdi Awaiting requested review from chrischdi

Assignees

@damdo damdo

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@mdbooth @openshift-ci-robot @damdo